Skip to content

[Snyk] Upgrade @contentstack/json-rte-serializer from 2.1.0 to 3.0.5#39

Open
shafeeqd959 wants to merge 1 commit intomainfrom
snyk-upgrade-766d2c2dc282e4aa7c231e1141bdf099
Open

[Snyk] Upgrade @contentstack/json-rte-serializer from 2.1.0 to 3.0.5#39
shafeeqd959 wants to merge 1 commit intomainfrom
snyk-upgrade-766d2c2dc282e4aa7c231e1141bdf099

Conversation

@shafeeqd959
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade @contentstack/json-rte-serializer from 2.1.0 to 3.0.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 6 versions ahead of your current version.

  • The recommended version was released 2 months ago.

Release notes
Package name: @contentstack/json-rte-serializer from @contentstack/json-rte-serializer GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @contentstack/json-rte-serializer from 2.1.0 to 3.0.5.

See this package in npm:
@contentstack/json-rte-serializer

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/7a549652-4fc7-484f-b6bd-0bf453540d60?utm_source=github&utm_medium=referral&page=upgrade-pr
@shafeeqd959 shafeeqd959 requested a review from a team as a code owner March 19, 2026 02:12
@github-actions
Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 4 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 4
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants